I'm not 100% sure if we want to do this. In some cases we have a circular dependency where we need to update Prism and CRuby at the same time. Do we merge to CRuby first, then send a PR to Prism? I'm not sure about the order of operations in that case.

Do we merge to CRuby first, then send a PR to Prism? I'm not sure about the order of operations in that case.

From my (limited) experience working on default gems, yes. There will be a PR including both library change AND CRuby test changes opened on ruby/ruby and gets merged there.
And the relevant changes will be ported back to the library with some local tests.

I think the point of running prism compilation test on CI is to identify the need to do so before we merge a PR.

@st0012 makes sense to me!

This is fine, thanks @st0012